View SR176-W41GE_1229601.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1/31 november 2004 sr176 13.56mhz short range contactless memory chip 176 bit user eeprom and 64 bits unique id features summary iso 14443 - 2 type b air interface compliant iso 14443 - 3 type b frame format compliant 13.56mhz carrier frequency 847.5khz subcarrier frequency 106kbit/s data transfer data transfer ? ask modulation from reader to tag ? bpsk coding from tag to reader 176-bit eeprom with write protect feature 64-bit unique identifier read block and write block (16 bits) internal tuning capacitor self-timed programming cycle 5ms programming time (typical) more than 100,000 erase/write cycles more than 40 years data retention figure 1. delivery forms wafer antenna (a3) antenna (a4) antenna (a5)
sr176 2/31 table of contents features summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 figure 1. delivery forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 summary description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 figure 2. pad connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 figure 3. die floor plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 ac1, ac0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 input data transfer from the reader to the sr176 (request frame) . . . . . . . . . . . . . . . . . . . . . 6 figure 4. received wave using ask modulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 character transmission format for request frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 request start of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 request end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 figure 5. sr176 request frame character format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 table 2. bit description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 figure 6. request start of frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 figure 7. request end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 output data transfer from the sr176 to the reader (answer frame) . . . . . . . . . . . . . . . . . . . . 8 character transmission format for answer frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 answer start of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 answer end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 8. emitted wave using bpsk sub-carrier modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 9. answer start of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 10.answer end of frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 transmission frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 11.example of a complete transmission frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 crc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 12.crc transmission rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 memory mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 13.sr176 memory mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 device identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 device selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 device operations (instructions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 14.state transition diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 initiate() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 15.initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 figure 16.initiate response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2
3/31 sr176 figure 17.8-bit chip_id format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 18.initiate frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . . . . . . 12 select(chip_id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 19.select request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 20.select response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 21.8-bit chip_id format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 22.select frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . . . . . . . 13 completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 23.completion request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 24.completion frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . . 14 read_block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 read the 64-bit uid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 25.read_block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 26.read_block response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 27.read_block frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . 15 figure 28.64-bit uid storage format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 write_block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 29.write_block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 30.write_block frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . 16 protect_block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 figure 31.protect_block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 3. bits in the lock_reg parameter, and in the otp lock_reg register . . . . . . . . . . . 17 figure 32.protect_block frame exchange between reader and sr176 . . . . . . . . . . . . . . . 17 get_protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 33.get_protection request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 34.get_protection response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 4. chip_id and lock_reg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 35.get_protection frame exchange between reader and sr176. . . . . . . . . . . . . . . 19 power on state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 sr176 command summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 figure 36.initiate frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . . . . . . 20 figure 37.select frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . . . . . . . 20 figure 38.completion frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . . 20 figure 39.read_block frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . 20 figure 40.write_block frame exchange between reader and sr176 . . . . . . . . . . . . . . . . . . 20 figure 41.protect_block frame exchange between reader and sr176 . . . . . . . . . . . . . . . 21 figure 42.get_protection frame exchange between reader and sr176 . . . . . . . . . . . . . . 21 maximum rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 5. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 dc and ac parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 6. operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 7. dc characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 8. ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
sr176 4/31 figure 43.ask modulated signal from the reader to the contactless device . . . . . . . . . . . . . . . . 24 figure 44.frame transmission between the reader and the contactless device . . . . . . . . . . . . . 24 figure 45.data jitter on the frame transmitted by the reader in ask . . . . . . . . . . . . . . . . . . . . . 24 package mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 46.a3 antenna specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 9. a3 antenna specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 figure 47.a4 antenna specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 10. a4 antenna specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 48.a5 antenna specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 11. a5 antenna specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 12. ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 8 appendix a.iso14443 type b crc calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 13. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5/31 sr176 summary description the sr176 is a contactless memory, powered by an externally transmitted radio wave. it contains 176 bits of user eeprom, fabricated with stmi- croelectronics cmos technology. the memory is organized as 16 blocks of 16 bits, of which 11 blocks are user accessible. the sr176 is accessed via the 13.56mhz carrier. incoming data are demodulated and decoded from the received amplitude shift keying modula- tion signal (ask). the modulation index of this sig- nal is 10%. outgoing data are generated by load variation using bit phase shift keying (bpsk) of a 847.5khz sub-carrier. the data transfer rate be- tween the sr176 and the reader is 106kbit/s in both reception and emission modes. the sr176 follows the iso 14443 part 2 type b recommendation for radio frequency power and signal interfacing. figure 2. pad connections the sr176 is principally designed for short range applications, such as object identification, that need a low cost and non-reusable tag. the sr176 does not include any anti-collision mechanism. it provides an ?addressed? selection mechanism to cope with cases where more than one tag is present within the range of the reader. table 1. signal names the sr176 contactless eeprom offers read and write random access in block mode. one block is composed by 16 bits. the device has an instruc- tion set containing seven commands: read_block write_block initiate select completion protect_block get_protection. the memory array of the sr176 is divided into two main areas: the unique identifier (uid) and the user eeprom. the uid is a 64-bit unique identi- fier, written by st during product manufacture. the user eeprom is divided into areas which can be write-protected so that they behave as rom. the write protection is activated using an otp lock bits register. it is possible to program the sr176 4-bit chip_id used by the select com- mand. its default value is fixed at the value 0 (0000 b ) by st. when correctly set, up to sixteen sr176 devices can be selected individually. figure 3. die floor plan signal description ac1, ac0. ac1 and ac0 pads must be directly bonded to the antenna. ac1 antenna coil ac0 antenna coil ai09057 ac1 sr176 ac0 power supply regulator bpsk load modulator ask demodulator 176 bit user eeprom ai09782 ac1 ac0
sr176 6/31 data transfer input data transfer from the reader to the sr176 (request frame) the reader that accesses the sr176 must gener- ate a 13.56mhz sinusoidal carrier wave on its an- tenna, with enough energy to ?tele-power? the sr176 device. the energy received on the sr176 antenna is transformed to a power supply voltage by a regulator, and to data bits through the ask demodulator. to decode correctly the information sent to the sr176, the reader must use a 10% am- plitude modulation of the 13.56mhz wave, as rep- resented (though not to scale) in figure 4. . the data transfer rate is 106 kbit/second. figure 4. received wave using ask modulation one bit time is 1/106khz ai09058 data bit transmit to the sr176 13.5mhz 10% ask modulation generated by the reader
7/31 sr176 character transmission format for request frame data bytes are transmitted and received by the sr176 as 10-bit characters, as shown in figure 5. , with the least significant bit (b 0 ) transmitted first. these characters, with the addition of the start of frame (sof) and the end of frame (eof), are grouped to form a command frame as shown in figure 11. . the frame includes an sof, instruc- tions, addresses, data, a crc and an eof as de- fined by iso14443-3 type b. if an error is detected during the data transfer, no error frame is generat- ed by the sr176, and the instruction is not execut- ed. each bit duration is referred to as an etu (ele- mentary time unit). one etu is equal to 9.44s (1/106khz). request start of frame the sof, as shown in figure 6. , consists of: ? one falling edge ? followed by 10 etus at logic 0 ? followed by one single rising edge ? followed by at least 2 etus (but no more than 3 etus) at logic 1. request end of frame the eof, as shown in figure 7. , consists of: ? one falling edge ? followed by 10 etus set to logic 0 ? followed by one single rising edge figure 5. sr176 request frame character format table 2. bit description figure 6. request start of frame figure 7. request end of frame bit description value b 0 start bit used to synchronize the transmission b 0 = 0 b 1 to b 8 information byte (command, address or data or crc) information byte sent, least significant bit first b 9 stop bit used to indicate the end of a character b 9 = 1 ai07664 1 etu start "0" stop "1" msb lsb information byte b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ai07665 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 000000000011 ai07666 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 0000000000
sr176 8/31 output data transfer from the sr176 to the reader (answer frame) the sr176 uses load modulation to return data to the reader. this modulation is achieved by modify- ing the sr176 current flow in its antenna. with ap- propriate detector circuitry, the reader is able to decode the information from the sr176. the data is transmitted using a bpsk coding of a 847.5khz sub-carrier frequency, f s , as specified in iso14443-2 type b, and as shown in figure 8. . character transmission format for answer frame the character format is the same as for the input data transfer ( figure 5. ). the transmitted frames include an sof, data, a crc and an eof (as shown in figure 11. ). like the input data transfer, in case of error, the reader does not emit any error code to the sr176, but must be able to detect and manage this situation. the data transfer rate is 106 kbit/second. answer start of frame the sof, as shown in figure 9. , consists of: ? 10 etus at logic 0 ?2 etus at logic 1 answer end of frame the eof, as shown in figure 10. , consists of: ? 10 etus at logic 0 ?2 etus at logic 1 figure 8. emitted wave using bpsk sub-carrier modulation figure 9. answer start of frame figure 10. answer end of frame data bit to transmit to the reader or ai09059 847.5khz bpsk modulation generated by the sr176 bpsk modulation at 847.5khz during one bit time (1/106khz) ai07665 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 000000000011 ai07665 etu b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 000000000011
9/31 sr176 transmission frame between the request and the answer data trans- fer, there is a guard time without ask and bpsk modulation, for a minimum period of t 0 =128/f s . this delay allows the reader to switch from trans- mission to reception mode, and is applied after each frame. after t 0 , the 13.56mhz carrier fre- quency is modulated by the sr176 at 847.5khz for a period of t 1 =128/f s , to allow the reader to syn- chronize. after t 1 , the first phase transition gener- ated by the sr176 represent the start bit (?0?) of the answer sof. after the falling edge of the an- swer eof, the reader has to wait for the minimum delay, t 2 , before sending a new request frame to the sr176. figure 11. example of a complete transmission frame crc the 16-bit crc that is used by the sr176 follows the iso14443 type b recommendation. for further information, see appendix a. . the initial register content is all ones: ffffh. a two-byte crc is appended to each request and each answer, within each frame, before the eof. the crc is calculated on all the bytes after the sof, up to the crc field. on reception of a request from a reader, the sr176 verifies that the crc value is valid. if it is invalid, it discards the frame and does not answer the reader. on reception of an answer from the sr176, it is recommended that the reader verify that the crc value is valid. if it is invalid, that choice of actions that are to be performed are the responsibility of the reader designer. the crc is transmitted least significant byte first. each byte is transmitted least significant bit first. figure 12. crc transmission rules sent by the reader sent by the sr176 input data transfer using ask sy n c f s =847.5khz sof cmd data crc crc eof data crc crc sof eo f sof ai09060 output data transfer using 847khz bpsk 10 bits 10 bits 10 bits 10 bits 10 bits 10 bits 10 bits 10 bits 12 bits 12 bits 12 bits 128/f s 128/f s t dr t 0 t 1 t 2 at 106kb/s crc 16 (8 bits) crc 16 (8 bits) lsbit msbit lsbit msbit lsbyte msbyte ai07667
sr176 10/31 memory mapping the sr176 is organized as 16 blocks of 16 bits, as shown in figure 13. . the first four blocks, from location 0 to 3, are used to store read-only data. they store the 64-bit uid. this value cannot be modified. blocks from locations 4 to 14 offer a 176-bit ee- prom user area in which the application can store its data values. block 15 contains the otp lock_reg and the programmed chip_id. the protect_block command is used to lock write access to blocks 4 to 15 in groups of two blocks. the get_protection command gives the sta- tus of the protection of blocks 4 to 15. figure 13. sr176 memory mapping device identification the sr176 has a 64-bit unique identifier (uid) which is written by stmicroelectronics during the manufacturing process. the uid is unique for each tag and cannot be altered. it is stored in a read only memory area (rom). in the sr176, the uid is stored in the first four blocks of the memory in blocks 0 to 3. device selection after introducing the device in the reader?s electro- magnetic field, the sr176 has to be activated by a initiate command. after this command, the sr176 is in the active state and waits for a se- lect command, as shown in figure 14. . the se- lect command specifies a 4-bit chip_id as a parameter. if the chip-id of the sr176 matches this parameter, the sr176 goes in the selected state, and memory blocks become available for read_block and write_block commands up to the reception of a completion command. if the chip_id does not match, the sr176 returns to, or stays in, the deselected state. write ac- cess rights are activated by the select com- mand. after the power on of the sr176, if the initiate command is not send or is not correctly generated, memory blocks will not be activated, and the sr176 will not respond to any command. block address msb lsb b15 16-bit block b7 b0 b8 description 0 1 2 3 uid0 uid1 uid2 uid3 64-bit uid rom 4 5 6 7 8 9 10 11 12 13 14 15 user area user area user area user area user area user area user area user area user area user area user area lockable eeprom lockable eeprom lockable eeprom lockable eeprom lockable eeprom lockable eeprom chip_id reserved otp lock_reg ai07699
11/31 sr176 device operations (instructions) all instructions, data and the crc are transmitted to the sr176 in 10-bit character format using ask modulation. the start bit (b 0 of the 10 bits) is sent first. the command frame received by the sr176 on the antenna is demodulated by the 10% ask demodulator, and is decoded by internal logic. pri- or to any operation, the sr176 must have been previously activated by an initiate command (as shown in figure 14. ). each frame transmitted to the sr176 must start with a start of frame, fol- lowed by one or more data characters, and is end- ed by two crc bytes and the end of frame. when an invalid frame is decoded by the sr176 (because of a wrong instruction or crc error), the memory does not send any error code. when a valid frame is received, the sr176 may have to send back data to the reader. for this, it sends 10-bit characters back, with sof, crc and eof, using the bpsk coding. the transfer is end- ed by the sr176 sending the eof. figure 14. state transition diagram ai09063b deactivated deselected power-off ready active selected initiate() in field out of field out of field select(chip_id) completion out of field out of field select(chip_id) select( = chip_id) select(chip_id) read_block() write_block() protect_block() get_protection() /
sr176 12/31 initiate() command code = 06h,00h prior to any other command, the sr176 must be activated by an initiate command. all other commands sent to the sr176 before the initiate are ignored. in response to receiving the initiate command, the sr176 sends back its chip_id, us- ing an 8-bit format ( figure 18. ). upon receiving a valid initiate command, the sr176 switches to the active state, where it will not answer to any new initiate command. once in the active state, the sr176 will remain in this state until it receives a valid select command. request parameters ( figure 15. ): ?none response parameters ( figure 16. ): ? chip_id (formatted as shown in figure 17. ) figure 15. initiate request format figure 16. initiate response format figure 17. 8-bit chip_id format figure 18. initiate frame exchange between reader and sr176 sof initiate crc l crc h eof ai07670b 06h 00h 8 bits 8 bits sof chip_id crc l crc h eof ai07701b 4 reserved bits + 4-bit id 8 bits 8 bits b7 b6 b5 b4 b3 b2 b1 b0 ai07700b reserved bits (block 15) b3 block 15 b0 4-bit chip_id of the sr176 ai09783 reader sr176 sof chip_id crc l crc h eof sof 06h crc l crc h eof 00h t 0 t 1
13/31 sr176 select(chip_id) command code = 0eh,(x.id)h prior to any memory access, the sr176 must have been set in the selected state by a se- lect() command. all other commands sent to the sr176 before the select(), except initiate(), are ignored. in response to receiving the se- lect() command, the sr176 sends back its chip_id, using an 8-bit format ( figure 22. ). any sr176 that is already in the selected state, and which receives a select() command that does not match its chip_id, is automatically put in the deselected state. the sr176 stays in the selected state up to the reception of a completion or a select with a non-matching chip_id. after a protect_block command, it is neces- sary to send a new select command in order to load enable the write access again in the internal logic. if a select is not send, the sr176 keeps the previous write access rights. request parameters ( figure 19. ): ? chip_id (formatted as shown in figure 21. ) response parameters ( figure 20. ): ? chip_id (formatted as shown in figure 21. ) figure 19. select request format figure 20. select response format figure 21. 8-bit chip_id format figure 22. select frame exchange between reader and sr176 sof select crc l crc h eof ai07702b 0eh 4 reserved bits + 4-bit id 8 bits 8 bits chip_id sof chip_id crc l crc h eof ai07703b 4 reserved bit + 4-bit id 8 bits 8 bits b7 b6 b5 b4 b3 b2 b1 b0 ai07704b test bits (block 15) b3 block 15 b0 4-bit chip_id of the sr176 ai09784 reader sr176 sof chip_id crc l crc h eof sof 0eh crc l crc h eof chip_id t 0 t 1
sr176 14/31 completion command code = 0fh when the completion command is received, the sr176 is put in the deactived state, and does not decode any new commands up to a pow- er-off, and a new power-on has occurred. this al- lows a new sr176 to be activated by an initiate command, without needing to remove the previ- ous ones. the sr176 does not generate any re- sponse when it executes a completion command ( figure 24. ). prior to any completion command, the sr176 must have been put in the selected mode by a select command. a sr176 which was not se- lected does not interpret this command. request parameters ( figure 23. ): ?none figure 23. completion request format figure 24. completion frame exchange between reader and sr176 sof completion crc l crc h eof ai07679b 0fh 8 bits 8 bits sof 0fh crc l crc h eof ai09785 reader sr176 no response
15/31 sr176 read_block command code = 08h,(x.ad) when receiving the read_block command, the sr176 reads the requested block and sends back its 16-bit value in response ( figure 27. ). the ad value of the four least significant bits of the ad- dress code, (x.ad) (b 3 to b 0 ) represents the block address to be read. for example, address 06h sends back the value of block 6. prior to any read_block command, the sr176 must have been set into the selected state. request parameters ( figure 25. ): ? address: to specify an address block from 00h to 0eh response parameters ( figure 26. ): ?data l : least significant byte ?data h : most significant byte read the 64-bit uid to read the complete 64-bit uid value from the sr176, the reader must provide a sequence of four read_block commands, in the following order ( figure 28. ): ? read_block @ 0 to get uid0 ? read_block @ 1 to get uid1 ? read_block @ 2 to get uid2 ? read_block @ 3 to get uid3 figure 25. read_block request format figure 26. read_block response format figure 27. read_block frame exchange between reader and sr176 figure 28. 64-bit uid storage format sof read_block crc l crc h eof ai07705b 08h 4 zero-bits + 4-bit address 8 bits 8 bits address sof data l crc l crc h eof ai07706b 8 bits 8 bits 8 bits data h 8 bits sof data l ai07707b data h reader sr176 crc l crc h eof sof 08h crc l crc h eof addr t 0 t 1 b15 uid2 b0 b15 uid1 b0 b15 uid0 b0 ai07708b b63 b0 uid3 b0 b15
sr176 16/31 write_block command code = 09h,(x.ad) prior to any write_block command, the sr176 must have been set into the selected state. when executing the write_block command, the sr176 overwrites the contents of the ad- dressed block with the 16-bit value that was sent in the command, provided that the block is avail- able and not write protected. the ad value of the four least significant bits of the address code (x.ad) (b 3 to b 0 ) represents the block address. for example, address 06h specifies that the data should be written in block 6. the sr176 does not generate any response when it executes a write_block command ( figure 30. ). the read- er must check after the programming time, t w , that the data bits were correctly programmed. block addresses between 0 to 3 cannot be ac- cessed using the write_block command (the command has no effect on these blocks). write ac- cess to block 15 is described in the section on the protect_block command. request parameters ( figure 29. ): ? address: address block from 4 to 14 ?data l : least significant byte ?data h : most significant byte figure 29. write_block request format figure 30. write_block frame exchange between reader and sr176 sof data l crc l crc h eof ai07709b data h 8 bits 8 bits 8 bits 8 bits write_block address 09h 4 zero-bits + 4-bit address data l ai07710b data h reader sr176 crc l crc h eof sof 09h addr no response
17/31 sr176 protect_block command code = 09h,0fh,00h,lock_reg prior to any protect_block command, the sr176 must have been set into the selected state. the protect_block command allows the write access to be blocked to memory blocks 4 to 15. it must be followed by a select() command. this re-initializes the write protection conditions to blocks 4 to 15. until then, the new protection set- ting is not taken into account by the sr176 logic. the sr176 does not generate any response when it executes a protect_block command ( figure 32. ). the reader must use the get_protection command to get the informa- tion on the protection status. the otp lock_reg controls the write-protec- tion on blocks 4 to 15, and is, itself, one-time pro- grammable. each ?1? in the lock_reg parameter indicates that the corresponding bit in the otp lock_reg should be set. each ?0? indicates that the corresponding bit should be left unchanged. once a bit in the otp lock_reg has been set to ?1?, it is not possible to reset it to ?0? and the corre- sponding memory blocks are forever write protect- ed (and behaves like rom). request parameters ( figure 31. ): ? lock_reg ( table 3. ) figure 31. protect_block request format table 3. bits in the lock_reg parameter, and in the otp lock_reg register figure 32. protect_block frame exchange between reader and sr176 lock reg parameter bit meaning block 15 bit meaning b 7 1: set b 15 of block 15 to ?1? 0: leave it unchanged b 15 1: write-protect blocks 14 and 15 0: allow write access b 6 1: set b 14 of block 15 to ?1? 0: leave it unchanged b 14 1: write-protect blocks 12 and 13 0: allow write access b 5 1: set b 13 of block 15 to ?1? 0: leave it unchanged b 13 1: write-protect blocks 10 and 11 0: allow write access b 4 1: set b 12 of block 15 to ?1? 0: leave it unchanged b 12 1: write-protect blocks 8 and 9 0: allow write access b 3 1: set b 11 of block 15 to ?1? 0: leave it unchanged b 11 1: write-protect blocks 6 and 7 0: allow write access b 2 1: set b 10 of block 15 to ?1? 0: leave it unchanged b 10 1: write-protect blocks 4 and 5 0: allow write access b 1 1: set b 9 of block 15 to ?1? 0: leave it unchanged b 9 1: write-protect blocks 2 and 3 0: allow write access b 0 1: set b 8 of block 15 to ?1? 0: leave it unchanged b 8 1: write-protect blocks 0 and 1 0: allow write access sof crc l crc h eof ai07711b lock_reg 00h 8 bits 8 bits 8 bits protect_block 09h 0fh 00h ai07712b lock_reg reader sr176 crc l crc h eof sof 09h 0fh no response
sr176 18/31 get_protection command code = 08h,0fh prior to any get_protection, the sr176 must have been set into the selected state. get_protection allows the protection status of memory blocks 4 to 15 to be read. when receiv- ing the get_protection command, the sr176 responds with the 16-bit value of block 15 ( figure 35. ). it gives the status of the lock_reg and the chip_id of the sr176. request parameters ( figure 33. ): ?none response parameters ( figure 34. ): ? chip_id: least significant byte ? lock_reg: most significant byte figure 33. get_protection request format figure 34. get_protection response format table 4. chip_id and lock_reg block 15 bits response parameter bits meaning b 15 lock_reg b 7 1: blocks 14 and 15 are write-protected (0: indicates that write-access is allowed) b 14 lock_reg b 6 1: blocks 12 and 13 are write-protected (0: indicates that write-access is allowed) b 13 lock_reg b 5 1: blocks 10 and 11 are write-protected (0: indicates that write-access is allowed) b 12 lock_reg b 4 1: blocks 8 and 9 are write-protected (0: indicates that write-access is allowed) b 11 lock_reg b 3 1: blocks 6 and 7 are write-protected (0: indicates that write-access is allowed) b 10 lock_reg b 2 1: blocks 4 and 5 are write-protected (0: indicates that write-access is allowed) b 9 lock_reg b 1 1: blocks 2 and 3 are write-protected (0: indicates that write-access is allowed) b 8 lock_reg b 0 1: blocks 0 and 1 are write-protected (0: indicates that write-access is allowed) b 4 to b 7 chip_id b 4 to b 7 reserved b 0 to b 3 chip_id b 0 to b 3 chip_id (value from 0h to fh) sof protect_block crc l crc h eof ai07713b 08h 0fh 8 bits 8 bits sof crc l crc h eof ai07714b 8 bits 8 bits 8 bits chip_id lock_reg 8 bits
19/31 sr176 figure 35. get_protection frame exchange between reader and sr176 power on state after power on, the sr176 is in the following state: ? the device is in the low power mode. ? the device is deselected. ? the device presents its highest impedance to the reader antenna field. ? it will not answer to any command except initiate. sof chip_id ai07716b lock_reg reader sr176 crc l crc h eof sof 08h crc l crc h eof 0fh t 0 t 1
sr176 20/31 sr176 command summary figure 36. initiate frame exchange between reader and sr176 figure 37. select frame exchange between reader and sr176 figure 38. completion frame exchange between reader and sr176 figure 39. read_block frame exchange between reader and sr176 figure 40. write_block frame exchange between reader and sr176 ai09783 reader sr176 sof chip_id crc l crc h eof sof 06h crc l crc h eof 00h t 0 t 1 ai09784 reader sr176 sof chip_id crc l crc h eof sof 0eh crc l crc h eof chip_id t 0 t 1 sof 0fh crc l crc h eof ai09785 reader sr176 no response sof data l ai07707b data h reader sr176 crc l crc h eof sof 08h crc l crc h eof addr t 0 t 1 data l ai07710b data h reader sr176 crc l crc h eof sof 09h addr no response
21/31 sr176 figure 41. protect_block frame exchange between reader and sr176 figure 42. get_protection frame exchange between reader and sr176 00h ai07712b lock_reg reader sr176 crc l crc h eof sof 09h 0fh no response sof chip_id ai07716b lock_reg reader sr176 crc l crc h eof sof 08h crc l crc h eof 0fh t 0 t 1
sr176 22/31 maximum rating stressing the device above the rating listed in the absolute maximum ratings" table may cause per- manent damage to the device. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not im- plied. exposure to absolute maximum rating con- ditions for extended periods may affect device reliability. refer also to the stmicroelectronics sure program and other relevant quality docu- ments. table 5. absolute maximum ratings note: 1. mil. std. 883 - method 3015 2. esd test: iso10373-6 for proximity cards symbol parameter min. max. unit t stg , h stg , t stg storage conditions wafer 15 25 c 23 months kept in its antistatic bag a3, a4, a5 15 25 c 40% 60% rh 2years i cc supply current on ac0 / ac1 ?20 20 ma v max input voltage on ac0 / ac1 ?7 7 v v esd electrostatic discharge voltage machine model 1 ?100 100 v human body model 1 ?1000 1000 v human body model 2 ?4000 4000 v
23/31 sr176 dc and ac parameters this section summarizes the operating and mea- surement conditions, and the dc and ac charac- teristics of the device. the parameters in the dc and ac characteristic tables that follow are de- rived from tests performed under the measure- ment conditions summarized in the relevant tables. designers should check that the operating conditions in their circuit match the measurement conditions when relying on the quoted parame- ters. table 6. operating conditions table 7. dc characteristics table 8. ac characteristics note: 1. all timing measurements were performed on a reference antenna with the following characteristics: external size: 75mm x 48mm number of turns: 3 width of conductor: 1mm space between 2 conductors: 0.4mm value of the coil: 1.4h tuning frequency: 14.4mhz. symbol parameter min. max. unit t a ambient operating temperature wafer ?20 85 c a3, a4, a5 ?20 85 c symbol parameter condition min max unit v cc regulated voltage 2.5 3.5 v v ret retromodulation induced voltage iso10373-6 20 mv c tun internal tuning capacitor 70pf at 13.56mhz 64 78 pf symbol parameter condition min max unit f cc external rf signal frequency 13.553 13.567 mhz mi carrier carrier modulation index mi=(a-b)/(a+b) 10 14 % t rfr ,t rff 10% rise and fall time 10% to 90% 0.5 1.5 s t rfsbl 10% modulation pulse width etu = 128/f cc 9.44 s t jit ask modulation data jitter coupler to sr176 - 2 + 2 s t min cd minimum time from carrier generation to first data from h-field min 40 s f s subcarrier frequency f cc /16 847.5 khz t 0 antenna reversal delay 128/f s 151 s t 1 synchronization delay 128/f s 151 s t 2 answer to new request delay 14 etu 132 s t dr time between request characters coupler to sr176 0 57 s t da time between answer characters sr176 to coupler 0 s t w programming time for write 5 ms
sr176 24/31 figure 43. ask modulated signal from the reader to the contactless device figure 44. frame transmission between the reader and the contactless device figure 45. data jitter on the frame transmitted by the reader in ask ai09061b f cc t min cd t rfr t rff a b t rfsbl ai09786 t dr t dr t da t da t da t 1 t 0 eof data sof data crc frame transmitted by the reader in ask frame transmitted by the sr176 in bpsk 847.5khz 0 1 0 1 0 11 0 11 start 0 ai09787 t jit t jit t jit t jit t jit t rfsbl t rfsbl t rfsbl t rfsbl t rfsbl
25/31 sr176 package mechanical figure 46. a3 antenna specification table 9. a3 antenna specification symbol parameter type min max unit a coil width 38 37.5 38.5 mm b coil length 38 37.5 38.5 mm a1 inlay width 43 42.5 43.5 mm b1 inlay length 43 42.5 43.5 mm overall thickness of copper antenna coil 110 90 130 m silicon thickness 180 165 195 m q unloaded q value 40 f nom unloaded free-air resonance 15.1 mhz p a h-field energy for device operation 0.5 114 a/m dba/m a b1 a1 ai09046b b
sr176 26/31 figure 47. a4 antenna specification table 10. a4 antenna specification symbol parameter type min max unit a coil width 15 14.5 15.5 mm b coil length 15 14.5 15.5 mm a1 inlay width 19 18.5 19.5 mm b1 inlay length 19 18.5 19.5 mm overall thickness of copper antenna coil 110 90 130 m silicon thickness 180 165 195 m q unloaded q value 30 f nom unloaded free-air resonance 14.5 mhz p a h-field energy for device operation 1.5 123.5 a/m dba/m ai07696b b a a1 b1
27/31 sr176 figure 48. a5 antenna specification table 11. a5 antenna specification symbol parameter type min max unit a coil width 42 41.5 42.5 mm b coil length 65 64.5 65.5 mm a1 inlay width 46 45.5 46.5 mm b1 inlay length 70 69.5 70.5 mm overall thickness of copper antenna coil 140 130 150 m silicon thickness 180 165 195 m q unloaded q value 30 f nom unloaded free-air resonance 14.8 mhz p a h-field energy for device operation 0.25 108 a/m dba/m a b a1 ai09071b b1
sr176 28/31 part numbering table 12. ordering information scheme note: devices are shipped from the factory with the memory content bits erased to 1. for a list of available options (speed, package, etc.) or for further information on any aspect of this device, please contact your nearest st sales office. example:sr176 ? w4 / xxx device type sr176 package w4 =180 m 15 m unsawn wafer sbn18= 180m 15 m bumped and sawn wafer on 8-inch frame a3t= 38mm x 38mm copper antenna on continuous tape a3s= 38mm x 38mm copper singulated adhesive antenna on tape a4t= 15mm x 15mm copper antenna on continuous tape a4s= 15mm x 15mm copper singulated adhesive antenna on tape a5t= 42mm x 65mm copper antenna on continuous tape a5s= 42mm x 65mm copper singulated adhesive antenna on tape customer code xxx = given by stmicroelectronics
29/31 sr176 appendix a. iso14443 type b crc calculation #include #include #include #include #define byte unsigned char #define ushortunsigned short unsigned short updatecrc(byte ch, ushort *lpwcrc) { ch = (ch^(byte)((*lpwcrc) & 0x00ff)); ch = (ch^(ch<<4)); *lpwcrc = (*lpwcrc >> 8)^((ushort)ch << 8)^((ushort)ch<<3)^((ushort)ch>>4); return(*lpwcrc); } void computecrc(char *data, int length, byte *transmitfirst, byte *transmitsecond) { byte chblock; ushortt wcrc; wcrc = 0xffff; // iso 3309 do { chblock = *data++; updatecrc(chblock, &wcrc); } while (--length); wcrc = ~wcrc; // iso 3309 *transmitfirst = (byte) (wcrc & 0xff); *transmitsecond = (byte) ((wcrc >> 8) & 0xff); return; } int main(void) { byte buffcrc_b[10] = {0x0a, 0x12, 0x34, 0x56}, first, second, i; printf("crc-16 g(x) = x^16 + x^12 + x^5 + 1?); printf("crc_b of [ "); for(i=0; i<4; i++) printf("%02x ",buffcrc_b[i]); computecrc(buffcrc_b, 4, &first, &second); printf("] transmitted: %02x then %02x.?, first, second); return(0);
sr176 30/31 revision history table 13. document revision history date rev. description of revision 23-sep-2002 1.0 document written 04-oct-2004 2.0 first public release of full datasheet 29-nov-2004 3.0 initiate() command specified.
31/31 sr176 information furnished is believed to be accurate and reliable. however, stmicroelectronics assumes no responsibility for the co nsequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of stmicroelectronics. specifications mentioned in this publicati on are subject to change without notice. this publication supersedes and replac es all information previously supplied. stmicroelectronics prod ucts are not authorized for use as critical components in life support devices or systems without express written approval of stmicroelectro nics. the st logo is a registered trademark of stmicroelectronics. all other names are the property of their respective owners ? 2004 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - belgium - brazil - canada - china - czech republic - finland - france - germany - hong kong - india - israel - ital y - japan - malaysia - malta - morocco - singapore - spain - sweden - switzerland - united kingdom - united states of america www.st.com

▲Up To Search▲

Price & Availability of SR176-W41GE

	To Download SR176-W41GE Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .